-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Compute API version and Fix the response of POST response #3053
Conversation
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
Code | Id | Source | Message |
---|---|---|---|
DescriptionMustNotBeNodeName | R3011 | Link | Description must not match the name of the node it is supposed to describe. Node name:'parameters' Description:'parameters' |
XmsExamplesRequired | D5001 | Link | Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations. |
AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback
Thanks for your co-operation.
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hyonholee please, when creating a new API version, we need two commits. The first one is a copy of the old one, and the second one should contain changes. In this case, reviewers can see the difference. https://github.com/Azure/azure-rest-api-specs/blob/master/.github/CONTRIBUTING.md#filenames-and-folder-structure
… API version update)
@ravbhatnagar new API version for Compute. |
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/compute/resource-manager/readme.md
|
@hyonholee - is there a response body in the final response with any of these POST operations?If yes, those will need to be modeled. I am guessing not, but just wanted to confirm. Looks fine. @sergey-shandar - feel free to merge based on response to above. |
} | ||
], | ||
"responses": { | ||
"200": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For all APis, please model a default error response whose schema complies with the error contract as per ARM RPC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ravbhatnagar Do you mean adding default response like this? Is it necessary? Or can I add it in another PR later?
@@ -151,6 +151,19 @@ directive: | |||
- TrackedResourceGetOperation | |||
|
|||
``` | |||
### Tag: package-2018-04-2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hyonholee Is there a reason why it doesn't match API version?
- API version: 2018-04-01
- Tag: package-2018-04-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sergey-shandar Oh, I just set the tag name to "package-2018-04-2" because "package-2018-04" already exists. Could you suggest a better tag name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hyonholee Oh, I see. It looks like 2018-04-01/disk.json
is shared. In this case, it's breaking changes, right? Do you change service behavior for disk
api version 2018-04-01
? Since the 2018-04-01
disk is already in stable folder, I would recommend to create a new api version in this case.
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Note that this PR is required to fix all POST (currently broken) operations with client library and Powershell including the following issues: |
Upgrade Compute API version to 2018-04-01 and Fix the response of all POST operation.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger